Context based action menu

ABSTRACT

A quick action menu system may be configured to perform operations that include: causing display of a graphical user interface (GUI) at a client device, the GUI comprising a display of a persistent icon at a position within the GUI; receiving a selection of the persistent icon from the client device; accessing user profile data associated with a user of the client device responsive to the input that selects the persistent icon; and causing display of a quick actions menu to display content associated with the user profile data.

PRIORITY APPLICATION

This application claims priority to U. S. Provisional Patent ApplicationSerial Number 63/363,891, filed Apr. 29, 2022, the disclosure of whichis incorporated by reference herein in its entirety.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally the field ofgraphical user interfaces (GUI), and more specifically to the selectivedisplay of content within GUI.

BACKGROUND

Due to the increased importance of mobile devices in a professionaldriver's daily workflow, ensuring the drivers are not distracted whiletheir vehicle is in-motion is an essential part of ensuring successfuland safe business operations. In particular, administrators want theirdrivers to physically interact with their device as little as possible,especially while the vehicle is in-motion. One way to reduce driverinteraction while in-motion is to selectively populate a driver's devicewith only contextually relevant information that they would normallyhave to search for. Accordingly, the disclosed system provides

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 is a block diagram showing an example system for exchanging data(e.g., sensor data and associated content) over a network in accordancewith some embodiments, wherein the system includes a quick action menusystem.

FIG. 2 is a block diagram illustrating various modules of a quick actionmenu system, according to certain example embodiments.

FIG. 3 is a flowchart depicting a method of selectively presentingcontent within a GUI, according to certain example embodiments.

FIG. 4 is a flowchart depicting a method of selectively presentingcontent within a GUI, according to certain example embodiments.

FIG. 5 is an interface diagram depicting a GUI presented by a quickaction menu system, according to certain example embodiments.

FIG. 6 is an interface diagram depicting a GUI presented by a quickaction menu system, according to certain example embodiments.

FIG. 7 is a block diagram illustrating components of a machine,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

As discussed above, professional drivers, such as truck drivers, areincreasingly reliant on mobile devices as a part of their dailyworkflows. For example, if a driver wants to view navigationinstructions while also checking their current Hours of Service (HoS),they would need to manually switch between applications displayed attheir mobile device. This can be very distracting and unsafe fordrivers. The disclosed system therefore provides an interface toselectively display the most contextually relevant information.

According to certain example embodiments, a quick action menu system maybe configured to perform operations that include: causing display of agraphical user interface (GUI) at a client device, the GUI comprising adisplay of a persistent icon at a position within the GUI; receiving aselection of the persistent icon from the client device; accessing userprofile data associated with a user of the client device responsive tothe input that selects the persistent icon; and causing display of aquick actions menu to display content associated with the user profiledata.

In some embodiments, the user profile data may include one or more of: aduty status associated with the user of the client device, wherein theduty status provides an indication of whether they are driving orstopped (e.g., fuel stop, tire check, load check, etc.); a driver's HoSat any given time, wherein the HoS indicates the maximum allowableworking hours for the driver, as well as how much rest the driver isrequired between shifts; Driver Vehicle Inspection Report (DVIR)information; route information, including names and locations ofupcoming stops; as well as a vehicle identifier and a traileridentifier.

An administrator of the quick action menu system may provide inputs toassign content to one or more elements found within the user profiledata associated with the user. For example, the administrator mayprovide inputs to configure information to be presented within the menuelement based on a driver's duty status at a given time or based on acurrent position of the driver along a route. In some embodiments, thecontent may be associated with a particular driver identifier, vehicleidentifier, a shipping identifier, or trailer identifier.

The content presented within the menu element may include a display ofcurrent statuses related to the user profile data, such as the driver'scurrent HoS, as well as a name and location associated with the nextstop along a current route of the driver. In some embodiments, thecontent may include messages received by the driver from a systemadministrator associated with the quick action menu system.

In some embodiments, an administrator of the quick action menu systemmay provide inputs to correlate one or more applications executed by theclient device to the user profile data associated with the user of theclient device. For example, the menu element may include a display ofone or more icons that comprise deep links to the correlatedapplications, such that selection of an icon from among the one or moreicons may cause the client device to execute a deep-link to thecorresponding application. As an illustrative example, the administratormay assign an application configured to present DVIR data, to a dutystatus (i.e., driving) associated with the user of the client device,such that upon receiving an input to select the persistent icon whileengaged in the duty status, the system may display a menu element thatinclude an icon corresponding with the application.

FIG. 1 is a block diagram showing an example system 100 for sampling airquality, according to certain example embodiments. The system 100includes one or more client devices 122 that host a number ofapplications including a client application 114.

Accordingly, each client application 114 is able to communicate andexchange data with another client application 114 and with the serverapplication 114 executed at the server system 108 via the network 106.The data exchanged between client applications 114, and between a clientapplication 114 and the server system 108, includes functions (e.g.,commands to invoke functions) as well as payload data (e.g., text,audio, video or other multimedia data).

The server system 108 provides server-side functionality via the network106 to a particular client application 114, and in some embodiments tothe vehicle gateway 102 and the system gateway 104. While certainfunctions of the system 100 are described herein as being performed byeither a client application 114, the vehicle gateway 102, the systemgateway 104, or by the server system 108, it will be appreciated thatthe location of certain functionality either within the clientapplication 114 or the server system 108 is a design choice. Forexample, it may be technically preferable to initially deploy certaintechnology and functionality within the server system 108, but to latermigrate this technology and functionality to the client application 114,or one or more processors of the vehicle gateway 102, or system gateway104, where there may be sufficient processing capacity.

The server system 108 supports various services and operations that areprovided to the client application 114. Such operations includetransmitting data to, receiving data from, and processing data generatedby the client application 114, the vehicle gateway 102, and the systemgateway 104. In some embodiments, the vehicle gateway 102 may include anodometer associated with a vehicle, as well as a GPS associated with thevehicle. In some embodiments, this data includes, message content,device information, geolocation information, persistence conditions,social network information, sensor data, and live event information, asexamples. In other embodiments, other data is used. Data exchangeswithin the system 100 are invoked and controlled through functionsavailable via graphical user interfaces (GUIs) of the client application114.

Turning now specifically to the server system 108, an ApplicationProgram Interface (API) server 110 is coupled to, and provides aprogrammatic interface to, an application server 112. The applicationserver 112 is communicatively coupled to a database server 118, whichfacilitates access to a database 120 that stores data associated withdata generated by the Vehicle gateway 102 and processed by theapplication server 112.

Dealing specifically with the API server 110, this server receives andtransmits data (e.g., sensor data, commands, and payloads) between theclient device 122 and the application server 112. Specifically, the APIserver 110 provides a set of interfaces (e.g., routines and protocols)that can be called or queried by the client application 114 in order toinvoke functionality of the application server 112. The API server 110exposes various functions supported by the application server 112,including account registration, login functionality, the transmission ofdata, via the application server 112, from a particular clientapplication 114 to another client application 114, the sending of sensordata (e.g., images, video, geolocation data, inertial data, temperaturedata, etc.) from a client application 114 to the server application 114,and for possible access by another client application 114, the settingof a collection of data, the retrieval of such collections, theretrieval of data, and the location of devices within a region.

The application server 112 hosts a number of applications andsubsystems, including a server application 114, and a quick action menusystem 124. According to certain example embodiments, the quick actionmenu system 124 is configured to perform operations to selectivelydisplay contextually relevant information within a menu element,responsive to selection of a persistent icon. Further details of thequick action menu system 124 can be found in FIG. 2 below.

The server application 114 implements a number of data processingtechnologies and functions, particularly related to the aggregation andother processing of data (e.g., sensor data generated by the vehiclegateway 102). As will be described in further detail, the sensor data,including temporal data, asset status data, and GPS data points,generated by the vehicle gateway 102 may be aggregated into collectionsassociated with a particular user account. Other processor and memoryintensive processing of data may also be performed server-side by theserver application 114, in view of the hardware requirements for suchprocessing.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with sensor data generated by the vehicle gateway102 and processed by the server application 114.

FIG. 2 is a block diagram 200 illustrating components of the quickaction menu system 124 that configure the quick action menu system 124to perform operations to selectively display contextually relevantinformation to a user, responsive to receiving an input that selects apersistent icon presented within a GUI of the client device 122,according to some example embodiments.

The quick action menu system 124 is shown as including user profilemodule 202, a user input module 204, a presentation module 206, and alocation module 208, all configured to communicate with each other(e.g., via a bus, shared memory, or a switch). Any one or more of thesemodules may be implemented using one or more processors 210 (e.g., byconfiguring such one or more processors to perform functions describedfor that module) and hence may include one or more of the processors210.

Any one or more of the modules described may be implemented usinghardware alone (e.g., one or more of the processors 210 of a machine) ora combination of hardware and software. For example, any moduledescribed of the quick action menu system 124 may physically include anarrangement of one or more of the processors 210 (e.g., a subset of oramong the one or more processors of the machine) configured to performthe operations described herein for that module. As another example, anymodule of the quick action menu system 124 may include software,hardware, or both, that configure an arrangement of one or moreprocessors 210 (e.g., among the one or more processors of the machine)to perform the operations described herein for that module. Accordingly,different modules of the quick action menu system 124 may include andconfigure different arrangements of such processors 210 or a singlearrangement of such processors 210 at different points in time.Moreover, any two or more modules of the quick action menu system 124may be combined into a single module, and the functions described hereinfor a single module may be subdivided among multiple modules.Furthermore, according to various example embodiments, modules describedherein as being implemented within a single machine, database, or devicemay be distributed across multiple machines, databases, or devices.

FIG. 3 is a flowchart depicting a method 300 of selectively presentingcontent within a GUI of a client device 122, according to certainexample embodiments. Operations of the method 300 may be performed bythe modules described above with respect to FIG. 2 . As shown in FIG. 3, the method 300 includes one or more operations 302, 304, 306, and 308.

At operation 302, the presentation module 206 causes display of a GUI ata client device 122, wherein the GUI comprises a display of a persistenticon at a position within the GUI. As discussed herein, a persistenticon may include a graphical icon which may be presented “persistently”within a GUI of the client device 122, regardless of what application isbeing executed by the client device 122, or whatever content is beingdisplayed within the GUI of the client device 122.

In some embodiments, the persistent icon may be presented within aheader element of the GUI. For example, the quick action menu system 124may be configured to display a header element within the GUI, whereinthe header element includes a display of one or more user selectableicons that include the persistent icon.

In some embodiments, the persistent icon may include a graphical elementthat may be moved or placed at a position within the GUI of the clientdevice 122, by a user or administrator associated with the client device122.

At operation 304, the user input module 204 receives an input thatselects the persistent icon from a user of the client device 122. Forexample, the client device 122 may comprise one or more I/O componentsconfigured to receive inputs from a user of the client device 122, suchas a tactile input.

In some embodiments, the user input module 204 may be configured toprovide an input to the quick action menu system 124 responsive to thedetection of some trigger condition. For example, the trigger conditionmay include: the detection of motion; determining that a vehicleassociated with the user of the client device 122 has transgressed athreshold speed; or determining that the vehicle associated with theuser of the client device 122 has entered into a geo-fenced location.

Responsive to receiving the input that selects the persistent icon, theuser profile module 202 accesses user profile data associated with auser of the client device 122. The user profile data may comprise: auser identifier associated with the user; a duty status associated withthe user of the client device, wherein the duty status provides anindication of whether they are driving or stopped (e.g., fuel stop, tirecheck, load check, etc.); a driver's HoS at any given time, wherein theHoS indicates the maximum allowable working hours for the driver, aswell as how much rest the driver is required between shifts; DVIRinformation; route information, including names and locations ofupcoming stops; as well as a vehicle identifier and a traileridentifier.

In some embodiments, an administrator associated with the quick actionmenu system 124 may provide inputs to correlate the various attributesfrom with the user profile data to content which may be presented to theuser within a menu element. Accordingly, the correlations may be hostedwithin the databases 120, such that the quick action menu system 124 mayaccess the database 120 to determine relevant content to be presented tothe user within the GUI of the client device 122.

Accordingly, at operation 308, the presentation module 206 generates andcauses display of a presentation of a menu element to selectivelydisplay relevant content to the user of the client device 122, based onthe user profile data associated with the user.

In some embodiments, the content may include various metrics associatedwith a vehicle, or with the user. The quick action menu system 124 maypresent various content based on a determination of the user's currentduty status or based on a current location of the user along a route.

For example, the content presented within the menu element may include adisplay of current statuses related to the user profile data, such asthe driver's current HoS, as well as a name and location associated withthe next stop along a current route of the driver. In some embodiments,the content may include messages received by the driver from a systemadministrator associated with the quick action menu system.

In some embodiments, the content may include icons that comprisedeep-links to one or more applications which may be relevant to a userof the client device 122 based on the user profile data associated withthe user. For example, the database 120 may include correlations ofvarious applications to user attributes indicated within the userprofile data, such as a user identifier, a vehicle identifier, a traileridentifier, etc.

Further details related to the menu element, and contents which may bepresented within the menu element are depicted in FIGS. 5, 6 and 7 .

FIG. 4 is a flowchart depicting a method 400 of selectively presentingcontent within a GUI of a client device 122, according to certainexample embodiments. Operations of the method 400 may be performed bythe modules described above with respect to FIG. 2 . In someembodiments, the method 400 may be performed as a precursor orsubroutine of operation 306 of the method 300 depicted in FIG. 3 . Asshown in FIG. 4 , the method 400 includes one or more operations 402,404, and 406.

In some embodiments, the quick action menu system 124 may be configuredto present content within the menu element based on a route associatedwith the user of the client device 122. For example, at operation 402,responsive to receiving an input that selects the persistent icon, thelocation module 208 may determine a current location associated with theclient device 122, wherein the current location may provide anindication of a status of the user along a route indicated within theuser profile data.

At operation 404, the user profile data module 202 accesses a route fromamong the user profile data associated with the user in order todetermine a next location along the route, based on the currentlocation.

At operation 406, the presentation module 206 causes display of apresentation of an indication of the next location along the routewithin the menu element at the client device 122. The indication of thenext location may for example include a display of a name or addressassociated with the location or may include a display of a map imagethat include the location.

FIG. 5 is an interface diagram 500 depicting a GUI 504 presented at aclient device 122 by the quick action menu system 124, according tocertain example embodiments. As seen in the interface diagram 500, theGUI 504 may include a display of a persistent icon 502 at a positionwithin the GUI 504.

As discussed in the methods 300, and 400, the persistent icon 502 may bepresented at a position within the GUI 504 regardless of whatapplication or content is being presented by the client device 122.Accordingly, a user may access a menu element to display a selection ofcurated contextually relevant content via a selection of the persistenticon 502.

FIG. 6 is an interface diagram 600 depicting a GUI 504 presented by thequick action menu system 124, that includes a menu element 602 toselectively display curated, contextually relevant content, according tocertain example embodiments.

As seen in FIG. 6 , the menu element 602 may include a display ofcontent 604, wherein the content may be curated by an administratorassociated with the quick action menu system 124. For example, asdiscussed above, an administrator of the quick action menu system 124may provide inputs to correlate various user attributes to the content604 presented within the menu element 602.

According to certain example embodiments, the content 604 may furthercomprise a set of icons 606, wherein the set of icons 606 comprisedeep-links to applications correlated with user profile data associatedwith the client device 122.

Consider an illustrative example from a user perspective. A user of theclient device 122 may provide an input to select the persistent icon 502from within the GUI 504 of the client device 122. Responsive toreceiving the input that selects the persistent icon 502, the quickaction menu system 124 accesses user profile data associated with theuser of the client device 122, wherein the user profile data provide anindication of various user attributes associated with the user,including the user's duty status, a vehicle identifier associated withthe user, a route associated with the user, and various shipping detailsassociated with the user. The quick action menu system 124 may therebygenerate a menu element that comprises a display of content based on theuser attributes of the user and causes display of a presentation of themenu element at a position within the GUI 504 of the client device 122.Accordingly, the user may easily access relevant information quickly andwithout the need to switch between applications executed by the clientdevice 122.

FIG. 7 is a block diagram illustrating components of a machine 700,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 7 shows a diagrammatic representation of the machine700 in the example form of a computer system, within which instructions710 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 700 to perform any one ormore of the methodologies discussed herein may be executed. As such, theinstructions 710 may be used to implement modules or componentsdescribed herein. The instructions 710 transform the general,non-programmed machine 700 into a particular machine 700 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 700 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 700 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 700 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a personal digitalassistant (PDA), an entertainment media system, a cellular telephone, asmart phone, a mobile device, a wearable device (e.g., a smart watch),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 710, sequentially or otherwise, that specify actions to betaken by machine 700. Further, while only a single machine 700 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 710 to perform any one or more of the methodologiesdiscussed herein.

The machine 700 may include processors 704, memory memory/storage 706,and I/O components 718, which may be configured to communicate with eachother such as via a bus 702. The memory/storage 706 may include a memory714, such as a main memory, or other memory storage, and a storage unit716, both accessible to the processors 704 such as via the bus 702. Thestorage unit 716 and memory 714 store the instructions 710 embodying anyone or more of the methodologies or functions described herein. Theinstructions 710 may also reside, completely or partially, within thememory 714, within the storage unit 716, within at least one of theprocessors 704 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine700. Accordingly, the memory 714, the storage unit 716, and the memoryof processors 704 are examples of machine-readable media.

The I/O components 718 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 718 that are included in a particular machine 700 will dependon the type of machine. For example, portable machines such as mobilephones will likely include a touch input device or other such inputmechanisms, while a headless server machine will likely not include sucha touch input device. It will be appreciated that the I/O components 718may include many other components that are not shown in FIG. 7 . The I/Ocomponents 718 are grouped according to functionality merely forsimplifying the following discussion and the grouping is in no waylimiting. In various example embodiments, the I/O components 718 mayinclude output components 726 and input components 728. The outputcomponents 726 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 728 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 718 may includebiometric components 730, motion components 734, environmentalenvironment components 736, or position components 738 among a widearray of other components. For example, the biometric components 730 mayinclude components to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 734 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environment components 736 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 738 mayinclude location sensor components (e.g., a Global Position system (GPS)receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 718 may include communication components 740 operableto couple the machine 700 to a network 732 or devices 720 via coupling722 and coupling 724 respectively. For example, the communicationcomponents 740 may include a network interface component or othersuitable device to interface with the network 732. In further examples,communication components 740 may include wired communication components,wireless communication components, cellular communication components,Near Field Communication (NFC) components, Bluetooth® components (e.g.,Bluetooth® Low Energy), Wi-Fi® components, and other communicationcomponents to provide communication via other modalities. The devices720 may be another machine or any of a wide variety of peripheraldevices (e.g., a peripheral device coupled via a Universal Serial Bus(USB)).

Moreover, the communication components 740 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 740 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components740, such as, location via Internet Protocol (IP) geo-location, locationvia Wi-Fi® signal triangulation, location via detecting a NFC beaconsignal that may indicate a particular location, and so forth.

GLOSSARY

“CARRIER SIGNAL” in this context refers to any intangible medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine, and includes digital or analog communications signals orother intangible medium to facilitate communication of suchinstructions. Instructions may be transmitted or received over thenetwork using a transmission medium via a network interface device andusing any one of a number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine that interfaces toa communications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smart phones, tablets, ultra books, netbooks,laptops, multi-processor systems, microprocessor-based or programmableconsumer electronics, game consoles, set-top boxes, or any othercommunication device that a user may use to access a network.

“COMMUNICATIONS NETWORK” in this context refers to one or more portionsof a network that may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), the Internet, a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), aplain old telephone service (POTS) network, a cellular telephonenetwork, a wireless network, a Wi-Fi® network, another type of network,or a combination of two or more such networks. For example, a network ora portion of a network may include a wireless or cellular network andthe coupling may be a Code Division Multiple Access (CDMA) connection, aGlobal System for Mobile communications (GSM) connection, or other typeof cellular or wireless coupling. In this example, the coupling mayimplement any of a variety of types of data transfer technology, such asSingle Carrier Radio Transmission Technology (1xRTT), Evolution-DataOptimized (EVDO) technology, General Packet Radio Service (GPRS)technology, Enhanced Data rates for GSM Evolution (EDGE) technology,third Generation Partnership Project (3GPP) including 3G, fourthgeneration wireless (4G) networks, Universal Mobile TelecommunicationsSystem (UMTS), High Speed Packet Access (HSPA), WorldwideInteroperability for Microwave Access (WiMAX), Long Term Evolution (LTE)standard, others defined by various standard setting organizations,other long range protocols, or other data transfer technology.

“MACHINE-READABLE MEDIUM” in this context refers to a component, deviceor other tangible media able to store instructions and data temporarilyor permanently and may include, but is not be limited to, random-accessmemory (RAM), read-only memory (ROM), buffer memory, flash memory,optical media, magnetic media, cache memory, other types of storage(e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or anysuitable combination thereof. The term “machine-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions. The term “machine-readable medium” shallalso be taken to include any medium, or combination of multiple media,that is capable of storing instructions (e.g., code) for execution by amachine, such that the instructions, when executed by one or moreprocessors of the machine, cause the machine to perform any one or moreof the methodologies described herein. Accordingly, a “machine-readablemedium” refers to a single storage apparatus or device, as well as“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices. The term “machine-readable medium”excludes signals per se.

“COMPONENT” in this context refers to a device, physical entity or logichaving boundaries defined by function or subroutine calls, branchpoints, application program interfaces (APIs), or other technologiesthat provide for the partitioning or modularization of particularprocessing or control functions. Components may be combined via theirinterfaces with other components to carry out a machine process. Acomponent may be a packaged functional hardware unit designed for usewith other components and a part of a program that usually performs aparticular function of related functions. Components may constituteeither software components (e.g., code embodied on a machine-readablemedium) or hardware components. A “hardware component” is a tangibleunit capable of performing certain operations and may be configured orarranged in a certain physical manner. In various example embodiments,one or more computer systems (e.g., a standalone computer system, aclient computer system, or a server computer system) or one or morehardware components of a computer system (e.g., a processor or a groupof processors) may be configured by software (e.g., an application orapplication portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a Field-Programmable Gate Array (FPGA) or an ApplicationSpecific Integrated Circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component”(or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In embodiments in which multiple hardwarecomponents are configured or instantiated at different times,communications between such hardware components may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware components have access. Forexample, one hardware component may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware component may then, at alater time, access the memory device to retrieve and process the storedoutput. Hardware components may also initiate communications with inputor output devices, and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)). The performance of certain of the operations may bedistributed among the processors, not only residing within a singlemachine, but deployed across a number of machines. In some exampleembodiments, the processors or processor-implemented components may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the processors or processor-implemented components may bedistributed across a number of geographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor)that manipulates data values according to control signals (e.g.,“commands,” “op codes,” “machine code,” etc.) and which producescorresponding output signals that are applied to operate a machine. Aprocessor may, for example, be a Central Processing Unit (CPU), aReduced Instruction Set Computing (RISC) processor, a ComplexInstruction Set Computing (CISC) processor, a Graphics Processing Unit(GPU), a Digital Signal Processor (DSP), an Application SpecificIntegrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC)or any combination thereof. A processor may further be a multi-coreprocessor having two or more independent processors (sometimes referredto as “cores”) that may execute instructions contemporaneously.

What is claimed is:
 1. A method comprising: causing display of agraphical user interface (GUI) at a client device, the GUI comprising adisplay of a persistent icon at a position within the GUI; receiving aselection of the persistent icon from the client device; accessing userprofile data associated with a user of the client device responsive tothe input that selects the persistent icon; and causing display of aquick actions menu to display content associated with the user profiledata.
 2. The method of claim 1, wherein the user profile data comprisesan indication of a duty status associated with the user of the clientdevice, and wherein the content corresponds with the duty status.
 3. Themethod of claim 1, wherein the method further comprises: receiving, froman administrator, an input that assigns the content to the user profiledata.
 4. The method of claim 3, wherein the user profile comprises oneor more of: a user identifier; a vehicle identifier; a traileridentifier; an indication of duty status; and a shipping identifier. 5.The method of claim 1, wherein the content includes one or moregraphical icons that comprise deep links to one or more applications. 6.The method of claim 1, wherein the user profile data comprises a routeassociated with the user of the client device, the route comprising oneor more locations, and the causing display of the quick actions menu todisplay the content associated with the user profile data furthercomprises: determining a current location of the client deviceresponsive to the selection of the persistent icon; determining a nextlocation based on the route and the current location of the clientdevice; and wherein the quick action menu includes an indication of thenext location.
 7. The method of claim 1, wherein the method furthercomprises: determining an Hours of Service (HoS) associated with theuser based on the user profile data; and wherein the quick actions menuincludes a presentation of the HoS.
 8. A system comprising: a memory;and at least one hardware processor to perform operations comprising:causing display of a graphical user interface (GUI) at a client device,the GUI comprising a display of a persistent icon at a position withinthe GUI; receiving a selection of the persistent icon from the clientdevice; accessing user profile data associated with a user of the clientdevice responsive to the input that selects the persistent icon; andcausing display of a quick actions menu to display content associatedwith the user profile data.
 9. The system of claim 8, wherein the userprofile data comprises an indication of a duty status associated withthe user of the client device, and wherein the content corresponds withthe duty status.
 10. The system of claim 8, wherein the operationsfurther comprise: receiving, from an administrator, an input thatassigns the content to the user profile data.
 11. The system of claim10, wherein the user profile comprises one or more of: a useridentifier; a vehicle identifier; a trailer identifier; an indication ofduty status; and a shipping identifier.
 12. The system of claim 8,wherein the content includes one or more graphical icons that comprisedeep links to one or more applications.
 13. The system of claim 8,wherein the user profile data comprises a route associated with the userof the client device, the route comprising one or more locations, andthe causing display of the quick actions menu to display the contentassociated with the user profile data further comprises: determining acurrent location of the client device responsive to the selection of thepersistent icon; determining a next location based on the route and thecurrent location of the client device; and wherein the quick action menuincludes an indication of the next location.
 14. The system of claim 8,wherein the operations further comprise: determining an Hours of Service(HoS) associated with the user based on the user profile data; andwherein the quick actions menu includes a presentation of the HoS.
 15. Anon-transitory machine-readable storage medium comprising instructionsthat, when executed by one or more processors of a machine, cause themachine to perform operations comprising: causing display of a graphicaluser interface (GUI) at a client device, the GUI comprising a display ofa persistent icon at a position within the GUI; receiving a selection ofthe persistent icon from the client device; accessing user profile dataassociated with a user of the client device responsive to the input thatselects the persistent icon; and causing display of a quick actions menuto display content associated with the user profile data.
 16. Thenon-transitory machine-readable storage medium of claim 15, wherein theuser profile data comprises an indication of a duty status associatedwith the user of the client device, and wherein the content correspondswith the duty status.
 17. The non-transitory machine-readable storagemedium of claim 15, wherein the operations further comprise: receiving,from an administrator, an input that assigns the content to the userprofile data.
 18. The non-transitory machine-readable storage medium ofclaim 17, wherein the user profile comprises one or more of: a useridentifier; a vehicle identifier; a trailer identifier; an indication ofduty status; and a shipping identifier.
 19. The non-transitorymachine-readable storage medium of claim 15, wherein the contentincludes one or more graphical icons that comprise deep links to one ormore applications.
 20. The non-transitory machine-readable storagemedium of claim 15, wherein the user profile data comprises a routeassociated with the user of the client device, the route comprising oneor more locations, and the causing display of the quick actions menu todisplay the content associated with the user profile data furthercomprises: determining a current location of the client deviceresponsive to the selection of the persistent icon; determining a nextlocation based on the route and the current location of the clientdevice; and wherein the quick action menu includes an indication of thenext location.